Patch Changes

• #10806 cb1540504 Thanks @ phryneas! - Fix a bug in PersistedQueryLink that would cause it to permanently skip persisted queries after a 400 or 500 status code.

• #10807 b32369592 Thanks @ phryneas! - PersistedQueryLink will now also check for error codes in extensions.

• #10982 b9be7a814 Thanks @ sdeleur-sc! - Update relayStylePagination to avoid populating startCursor when only a single cursor is present under the edges field. Use that cursor only as the endCursor.

• #10962 772cfa3cb Thanks @ jerelmiller! - Remove useGETForQueries option in BatchHttpLink.Options type since it is not supported.

Potentially breaking change in PersistedQueryLink

Previously, if the PersistedQueryLink encountered a single 400 or 500 error, it would stop sending any persisted queries in the future. This allowed you to use the link even if a server had no support for persisted queries.

We have decided to change this behavior, so now the PersistedQueryLink will only stop trying to send query hashes if the server responds with a PERSISTED_QUERY_NOT_SUPPORTED error code as it was unclear whether a 400 or 500 status code was in fact because the server did not support persisted queries.

If you relied on the previous behaviour, maybe because you were communicating with a server that might or might not support persisted queries, but would return with a different kind of error, you can use the disable option callback to override this behavior like this:

createPersistedQueryLink({
  // ... other options ...
  disable({ operation }){
    const { response } = operation.getContext();
    return (
      response &&
      response.status &&
      (response.status === 400 || response.status === 500)
    );
  }
})

Alternatively, consider removing the link entirely when your server does not support persisted queries.

Patch Changes

• #10891 ab42a5c08 Thanks @ laverdet! - Fixes a bug in how multipart responses are read when using @ defer. When reading a multipart body, HttpLink no longer attempts to parse the boundary (e.g. "---" or other boundary string) within the response data itself, only when reading the beginning of each mulitpart chunked message.

• #10789 23a4e1578 Thanks @ phryneas! - Fix a bug where other fields could be aliased to __typename or id, in which case an incoming result would be merged into the wrong cache entry.

Patch Changes

• #10764 1b0a61fe5 Thanks @ phryneas! - Deprecate useFragment returnPartialData option

• #10810 a6252774f Thanks @ dleavitt! - Fix type signature of ServerError.

  In <3.7 HttpLink and BatchHttpLink would return a ServerError.message of e.g. "Unexpected token 'E', \"Error! Foo bar\" is not valid JSON" and a ServerError.result of undefined in the case where a server returned a >= 300 response code with a response body containing a string that could not be parsed as JSON.

  In >=3.7, message became e.g. Response not successful: Received status code 302 and result became the string from the response body, however the type in ServerError.result was not updated to include the string type, which is now properly reflected.

Patch Changes

• #10805 a5503666c Thanks @ phryneas! - Fix a potential memory leak in SSR scenarios when many persistedQuery instances were created over time.

• #10718 577c68bdd Thanks @ Hsifnus! - Delay Concast subscription teardown slightly in useSubscription to prevent unexpected Concast teardown when one useSubscription hook tears down its in-flight Concast subscription immediately followed by another useSubscription hook reusing and subscribing to that same Concast

Patch Changes

• #10735 895bcdcff Thanks @ alessbell! - If a multipart chunk contains only hasNext: false, immediately complete the observable.

Patch Changes

• #10586 4175af594 Thanks @ alessbell! - Improve WebSocket error handling for generic Event received on error. For more information see https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/error_event.

• #10411 152baac34 Thanks @ lovasoa! - Simplify error message generation and make 'undefined' an impossible message string.

• #10592 cdb98ae08 Thanks @ alessbell! - Adds support for multipart subscriptions in HttpLink.

• #10698 38508a251 Thanks @ jerelmiller! - Changes the behavior of useLazyQuery introduced in #10427 where unmounting a component before a query was resolved would reject the promise with an abort error. Instead, the promise will now resolve naturally with the result from the request.

  Other notable fixes:

  • Kicking off multiple requests in parallel with the execution function will now ensure each returned promise is resolved with the data from its request. Previously, each promise was resolved with data from the last execution.
  • Re-rendering useLazyQuery with a different query document will now ensure the execution function uses the updated query document. Previously, only the query document rendered the first time would be used for the request.

• #10660 364bee98f Thanks @ alessbell! - Upgrades TypeScript to v5. This change is fully backward-compatible and transparent to users.

• #10597 8fb9d190d Thanks @ phryneas! - Fix a bug where an incoming cache update could prevent future updates from the active link.

• #10629 02605bb3c Thanks @ phryneas! - useQuery: delay unsubscribe to fix race conditions

Patch Changes

• #9438 52a9c8ea1 Thanks @ dciesielkiewicz! - Ensure the client option passed to useMutation's execute function is used when provided. Previously this option was ignored.

• #9124 975b923c0 Thanks @ andrebrantom! - Make ApolloClient.writeQuery and ApolloClient.writeFragment behave more like cache.writeQuery and cache.writeFragment by returning the reference returned by the cache.

Patch Changes

• #10560 a561ecf43 Thanks @ benjamn! - Keep __typename fragment when it does not contain @ client directive and strip out inline fragments which use a @ client directive. Thanks @ Gazler and @ mtsmfm!

• #10560 251a12806 Thanks @ benjamn! - Refactor removeDirectivesFromDocument to fix AST ordering sensitivities and avoid 1/3 AST traversals, potentially improving performance for large queries

Patch Changes

• #7555 45562d6fa Thanks @ TheCeloReis! - Adds TVariables generic to GraphQLRequest and MockedResponse interfaces.

• #10526 1d13de4f1 Thanks @ benjamn! - Tolerate undefined concast.sources if complete called earlier than concast.start

• #10497 8a883d8a1 Thanks @ nevir! - Update SingleExecutionResult and IncrementalPayload's data types such that they no longer include undefined, which was not a valid runtime value, to fix errors when TypeScript's exactOptionalPropertyTypes is enabled.